This forum is closed to new posts and
responses. Individual names altered for privacy purposes. The information contained in this website is provided for informational purposes only and should not be construed as a forum for customer support requests. Any customer support requests should be directed to the official HCL customer support channels below:
RE: Extended ACL should do the trick (re: Registering web users with Secondary NAB) ~Rex Zekgeroplopettu 18.Jul.03 11:55 AM a Web browser Domino Server 6.0.1All Platforms
Nice idea Rod, but even if the user can't see the web people, the server can.
And if you (internal people) send a mail to one of the external people (because you've see it somewhere), the server solve this, and send the mail to the person :-(.
As i've posted on your site Jake, if you have separated server for internal and web usage (i hope it), you can use the old, but still good cascading system on the web server.
In this case, only this server can check the name, and can use it for authentication or mail.
If a internal person need to have access to this db, make a replica with appropriate ACL on the internal server.
Another solution is to create a new domain, and a new web server, with the master Cert.id, and in this case everything is solved by itself, except that you need more $$$$ for the server and the licence.
I've used the two solutions in the real live and it work perfectly in v5 & 6